Repository navigation
BlockVectra joins the Ethereum and Arbitrum RPC pages (#3573) - #3574
Merged
Merged
Conversation
Its keyless public routes for Ethereum and Arbitrum One are probed by the
rpc-capabilities harness like the other public providers on those pages,
on the same 60 s tick from the same three regions, with no special
treatment.
Checked by hand before wiring (2026-11-07, about 1 req/s from Europe):
chain id 1 and 42161, eth_getBlockByNumber("latest", false) answers, the
head 0 to 1 block behind PublicNode, 132 to 203 ms. One call in ten on
the Ethereum route came back -32005 "public chain pool is busy"; in
production that counts against its success rate like any refusal.
Base is NOT added: its route answers -32010 "node is syncing" to every
call. It goes on hold until BlockVectra says the node has caught up.
An arrival on two benches, so the four cache keys move (bench-unfiltered-v189,
all-benchmarks-v182, bench-filters-v107, providers-v62) and the
provider-set guard is re-pinned.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BlockVectra joins the Ethereum and Arbitrum RPC pages (#3573)
Its keyless public routes for Ethereum and Arbitrum One are probed by the
rpc-capabilities harness like the other public providers on those pages,
on the same 60 s tick from the same three regions, with no special
treatment.
Checked by hand before wiring (2026-11-07, about 1 req/s from Europe):
chain id 1 and 42161, eth_getBlockByNumber("latest", false) answers, the
head 0 to 1 block behind PublicNode, 132 to 203 ms. One call in ten on
the Ethereum route came back -32005 "public chain pool is busy"; in
production that counts against its success rate like any refusal.
Base is NOT added: its route answers -32010 "node is syncing" to every
call. It goes on hold until BlockVectra says the node has caught up.
An arrival on two benches, so the four cache keys move (bench-unfiltered-v189,
all-benchmarks-v182, bench-filters-v107, providers-v62) and the
provider-set guard is re-pinned.